Data movement between different cell regions in non-volatile memory

ABSTRACT

According to one embodiment, a memory system includes a non-volatile memory array with a plurality of memory cells. Each memory cell is a multilevel cell to which multibit data can be written. The non-volatile memory array includes a first storage region in which the multibit data of a first bit level is written and a second storage region in which data of a second bit level less than the first bit level is written. A memory controller is configured to move pieces of data from the first storage region to the second storage region based on the number of data read requests for the pieces of data received over a period of time or on external information received from a host device that sends read requests.

CROSS-REFERENCE TO RELATED APPLICATION

This application is based upon and claims the benefit of priority fromJapanese Patent Application No. 2020-136452, filed Aug. 12, 2020, theentire contents of which are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to a memory system.

BACKGROUND

In order to increase memory capacity, a multilevel storage technique canbe used in a memory system. When the multilevel storage technique isused, the number of bits of data that can be recorded in each memorycell increases, however, a reading speed of the stored data and awriting speed for recording the data in the memory system are likely tobe slower.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a configuration of a memory systemaccording to a first embodiment.

FIG. 2 is a block diagram showing a configuration of a memory controlleraccording to a first embodiment.

FIG. 3 shows a memory map of a NAND memory according to a firstembodiment.

FIG. 4 depicts a management table for tracking the number of times userdata is read in a first embodiment.

FIG. 5 is a flowchart of update processing of a management tableaccording to a first embodiment.

FIG. 6 is a flowchart of user data movement processing according to afirst embodiment.

FIG. 7 is a flowchart of user data movement processing when garbagecollection processing is performed according to a first embodiment.

FIG. 8 is a flowchart of data movement processing according to a secondembodiment.

FIG. 9 shows a configuration of a management table for tracking thenumber of cache hits and the number of cache misses when reading userdata according to a third embodiment.

FIG. 10 is a flowchart of update processing of a management tableaccording to a third embodiment.

FIG. 11 is a flowchart of user data movement processing according to athird embodiment.

DETAILED DESCRIPTION

Embodiments provide a memory system that moves data whose readingfrequency is high to a high-speed readable storage region.

In general, according to one embodiment, a memory system, includes anon-volatile memory array having a plurality of memory cells. Eachmemory cell is a multilevel cell to which multibit data can be written.The non-volatile memory array includes a first storage region in whichthe multibit data of a first bit level is written and a second storageregion in which data of a second bit level less than the first bit levelis written. A memory controller is configured to move pieces of datafrom the first storage region to the second storage region based on thenumber of data read requests for the pieces of data received over aperiod of time or on external information received from a host device orthe like.

Hereinafter, certain example embodiments will be described withreference to the drawings.

First Embodiment

FIG. 1 is a block diagram showing a configuration of a memory systemaccording to the first embodiment. A memory system 1 can be connected toa host device 2 (“host 2”). FIG. 1 shows the memory system 1 connectedto the host 2.

The host 2 is, for example, a personal computer, a smartphone, or thelike. The host 2 includes a central processing unit (CPU) 2 a as aprocessor, an ROM, and a DRAM 2 b.

The memory system 1 includes a memory controller 3 and a plurality ofNAND flash memories 4 (“NAND memories 4”). In the present example twoNAND memories 4 are depicted.

Each NAND memory 4 is a semiconductor storage device including a memorycell array 4 a and a control circuit (not separately depicted). Thememory cell array 4 a includes a plurality of memory cells MT. N-bitdata can be written into each memory cell MT, where here N is an integerof 2 or more. The memory cell MT is thus a multilevel cell such as atriple-level cell (TLC) capable of storing 3-bit data or a quad-levelcell (QLC) capable of storing 4-bit data. Here, an example in which thememory cell MT is a QLC memory cell will be described.

In response to a request from the host 2, the memory system 1 storesuser data (“data”) received from the host 2 in each NAND memory 4 orreads the data previously stored in the NAND memories 4 and outputs theread data to the host 2. Specifically, the memory system 1 writes thedata into each NAND memory 4 as a page unit in response to a writerequest from the host 2, and reads the data from each NAND memory 4 inresponse to a read request from the host 2.

Here, the memory system 1 includes the plurality of NAND memories 4,however, in certain examples, the memory system might include only oneNAND memory 4. The memory system 1 may be a memory card in which thememory controller 3 and the plurality of NAND memories 4 are integratedas one package, or may be a solid-state drive (SSD).

FIG. 2 is a block diagram showing a configuration of the memorycontroller 3. The memory controller 3 controls writing and reading ofthe data into and from each NAND memory 4. The memory controller 3controls the writing of the data into a NAND memory 4 in response to thewrite request from the host 2. Specifically, the memory controller 3writes the data into each NAND memory 4 in a page unit of apredetermined size. Furthermore, the memory controller 3 controls thereading of the data from each NAND memory 4 in response to the readrequest from the host 2.

The memory controller 3 includes a central processing unit (CPU) 11 as aprocessor, an ROM 12, an RAM 13, an error detection and correction (ECC)circuit 14, a memory buffer 15, a host interface circuit 16 (“host I/F16”), and a memory interface circuit 17 (“memory I/F 17”). The CPU 11,the ROM 12, the RAM 13, the ECC circuit 14, the memory buffer 15, thehost I/F 16, and the memory I/F 17 are connected to each other by aninternal bus 18.

The CPU 11 controls each sub-unit of the memory system 1 by executingone or more programs stored in the ROM 12. When the CPU 11 receives arequest from the host 2 via the host I/F 16, the CPU 11 performs variouscontrols by executing the program(s) according to the request. Forexample, the CPU 11 instructs the memory I/F 17 to write the data intoeach NAND memory 4 according to the request from the host 2.Furthermore, the CPU 11 instructs the memory I/F 17 to read the datafrom each NAND memory 4 according to a request from the host 2.

When the CPU 11 receives a write request from the host 2, the CPU 11selects a storage region on one or more NAND memory 4 for the user data(corresponding to the write request) that has been stored in the memorybuffer 15. That is, the CPU 11 manages a write destination of the userdata. A correspondence between a logical block address LBA of the userdata received from the host 2 and a physical block address PBAindicating the storage region on a NAND memory 4 at which the user datais stored can be determined based on a logical-to-physical addressconversion table. The logical-to-physical address conversion table canbe referred to as a logical-to-physical table or more simply as a L2Ptable. The L2P table stores data in which the logical block address LBAused when the host 2 accesses the memory system 1 and the physical blockaddress PBA in the memory system 1 have a one-to-one correspondence.

Further, when the CPU 11 receives the data read request from the host 2,the CPU 11 refers to the L2P table for the logical block address LBAspecified by the read request, and thus identifies the correspondingphysical block address PBA, and then instructs the memory I/F 17 to readthe data from the physical block address PBA. That is, when the CPU 11receives the request from the host 2, the CPU 11 identifies the physicalblock address corresponding to the logical block address LBA related tothe request, and then performs the writing and the reading of the dataaccordingly.

The ROM 12 stores various programs and various types of data. The RAM 13temporarily stores the various types of data and the like. Anumber-of-times management table and the L2P table are stored in the RAM13. The number-of-times management table TBL (“management table TBL”) isfor tracking the number of times data has been read. The managementtable TBL is stored in a storage region 13 a of the RAM 13. The L2Ptable is stored in a storage region 13 b of the RAM 13.

The ECC circuit 14 encodes the user data to be written and subsequentlydecodes the user data as read from each NAND memory 4.

The memory buffer 15 temporarily stores the user data received from thehost 2. Furthermore, the memory buffer 15 temporarily stores the userdata that has been read from a NAND memory 4. The memory buffer 15 is,for example, a general-purpose memory such as a static random accessmemory (SRAM) or a dynamic random access memory (DRAM).

The host I/F 16 performs processing according to a predeterminedinterface standard with the host 2. The host I/F 16 outputs the requestsand the user data received from the host 2 to the internal bus 18, andtransmits the user data that has been read from a NAND memory 4 and aresponse to a request from the CPU 11 and the like to the host 2.

Under the control of the CPU 11, the memory I/F 17 performs processingrelated to the writing of the data into each NAND memory 4 and thereading of the data from the NAND memories 4.

FIG. 3 shows a memory map of each NAND memory 4. As described above, theNAND memory 4 can store 4-bit data in each memory cell MT. An arrow MAindicates that the user data is moved from a QLC region to an address inanother region (a pseudo single level cell (pSLC) region).

A data storage region in each NAND memory 4 has a pseudo single levelcell (pSLC)) region and a QLC region. The pSLC region and the QLC regionin the data storage region of each NAND memory 4 are set in advance inthis example. The memory controller 3 can write the user data into thepSLC region or the QLC region. The memory controller 3 can also read theuser data from the pSLC region and the QLC region based on the logicalblock address LBA related to the request from the host 2.

The pSLC region is a storage region in which 1-bit data is written intoa pseudo single level cell (pSLC). In each of the pseudo single levelcells (pSLCs), 4-bit data could be written, but only 1-bit data iswritten. The writing of the data into the pSLC region is specified by acommand from the memory controller 3. Therefore, the memory system. 1includes a recording mode (pSLC mode) in which 1-bit data is written inthe memory cells MT in the pSLC region, and another recording mode inwhich 4-bit data is written in the memory cells MT in the QLC region.The writing time of data into the pSLC region is shorter than thewriting time of the same data into the QLC region. Furthermore, thereading time of data stored in the pSLC region is shorter than a readingtime of data stored in the QLC region.

When the memory controller 3 receives a write request of user data fromthe host 2, the memory controller 3 refers to (that is, searches) theL2P table and identifies the physical block address PBA corresponding tothe logical block address LBA related to the request. The memorycontroller 3 writes the user data into the storage region at theidentified physical block address PBA.

When the memory controller 3 receives a read request for user data fromthe host 2, the memory controller 3 refers to (that is, searches) theL2P table and identifies the physical block address PBA corresponding tothe logical block address LBA related to the request. The memorycontroller 3 reads the user data from the storage region at theidentified physical block address PBA.

As described above, each memory cell MT in the pSLC region is a memoryregion in which 1-bit data is written. Each memory cell MT in the pSLCregion could store 4-bit data (that is, memory cells MT in the pSLCregion have the same structure as the memory cells MT in the QLCregion), but is used only to store 1-bit data. Therefore, the pSLCregion generally has a faster writing speed and a faster reading speedthan the QLC region. The memory controller 3 writes user data into thepSLC region in the recording mode by which 1-bit data is written.

Various types of parameter data, various programs, and the like can bestored in the pSLC region. When power is turned on, the variousparameter data and the like is read from the pSLC region into the memorycontroller 3 and stored in the RAM 13. The various types of parameterdata and the like of the RAM 13 are used during operations of the memorysystem 1. The various types of parameter data and the like may beupdated from time to time. When the power is turned off, the memorycontroller 3 writes the various parameter data and the like from the RAM13 into the pSLC region of one or more NAND memory 4.

Each memory cell MT in the QLC region is a memory region in which 4-bitdata is written. The memory controller 3 writes the user data in the QLCregion in the recording mode in which 4-bit data is written.

In the first embodiment, the user data whose reading frequency is highcan be stored in the pSLC region. When the memory controller 3 receivesa read request of the user data from the host 2, the memory controller 3counts (tracks) the number of the read requests received for eachlogical block address LBA over time.

FIG. 4 shows a configuration of the management table TBL for tracking,by logical block address LBA, the number of times user data is read. Themanagement table TBL includes addresses of the logical block address LBAand information on the number of times the logical block address hasbeen read previously. The addresses in this example are head addressesof the logical block address LBA. The management table TBL stores theinformation on the number of times of the reading for each address. Thatis, the management table TBL stores information about the number oftimes data has been read from the logical block address LBA included inthe read request from the host 2.

In FIG. 4 , in order to facilitate understanding, logical blockaddresses of the pSLC region are collectively shown on an upper portionof the number-of-times management table TBL, and logical block addressesof the QLC region are collectively shown below the pSLC region. Suchdiscrete grouping is not necessarily required.

Next, an operation of the memory controller 3 will be described.

When the memory controller 3 receives the read request from the host 2,the memory controller 3 executes reading processing of the user data,and executes management processing of the number of the read requests asbackground processing of the reading processing. Here, the number of theread requests for each address is managed. When the CPU 11 receives theread request from the host 2, the CPU 11 executes update processing ofthe management table TBL.

FIG. 5 is a flowchart showing an example of a flow of the updateprocessing of the management table TBL. The processing in FIG. 5 isperformed by the CPU 11 reading the programs stored in the ROM 12 of thememory controller 3, loading the programs into the RAM 13, and executingthe programs.

The CPU 11 determines whether a read request from the host 2 has beenreceived (S1). When the read request is not received (S1; NO), the CPU11 does not perform the update processing of the management table TBL.

When the read request from the host 2 is received (S1; YES), the CPU 11manages the number of the read requests of the logical block address LBA(S2). In S2, the update processing of the number of the read requestsdata of the logical block address LBA included in the read request inthe management table TBL is performed. That is, when the memorycontroller 3 receives the read request from an external device (host 2),the memory controller 3 increments the number of the read requests ofthe logical address (LBA) of the user data related to the read request.

That is, the memory controller 3 updates the number of the read requestsof the address (logical block address LBA) of the user data every timethe read request is received from the host 2. As a result, the number ofthe read requests data for each address of the user data is stored inthe management table TBL.

FIG. 6 is a flowchart showing an example of a flow of user data movementprocessing. The processing of FIG. 6 may be executed when the processingof the read request from the host 2 is executed, or may be executed whenpredetermined processing other than the read request processing such asgarbage collection processing and compaction processing is executed, ormay be executed at a predetermined cycle.

The CPU 11 searches the management table TBL (S11), and determineswhether there is a logical block address LBA in which the number of theread requests is greater than or equal to a predetermined threshold THin the logical block address LBA of the user data stored in the QLCregion (S12). That is, the CPU 11 reads the number of the read requestsin the management table TBL for the user data stored in the QLC region,and determines whether there is a logical block address LBA for whichthe number of the read requests is greater than or equal to thepredetermined threshold TH.

When there is no logical block address LBA for which the number of theread requests is greater than or equal to the predetermined threshold THin the QLC region (S12; NO), the CPU 11 does not perform the user datamovement processing.

When there is a logical block address LBA for which the number of theread requests is greater than or equal to the predetermined threshold THin the QLC region (S12; YES), the CPU 11 moves the user datacorresponding to the logical block address LBA for which the number ofthe read requests is greater than or equal to the predeterminedthreshold TH from the QLC region to the pSLC region (S13). That is, whenthe number of the read requests is greater than or equal to thepredetermined threshold TH, the memory controller 3 performs themovement processing on the user data whose number of the read requestsis greater than or equal to the predetermined threshold TH.

After moving the user data, the CPU 11 updates the L2P table to reflectthe movement (S14). That is, in order to change the physical blockaddress PBA of the user data corresponding to the moved logical blockaddress LBA, the memory controller 3 updates an address conversion table(L2P table) of the NAND memory 4 after performing the movementprocessing on the data.

When the processing shown in FIG. 6 is executed every time there is theread request from the host 2, in S13, the movement processing isperformed on one user data corresponding to one logical block addressLBA. However, when the garbage collection processing is performed, whenthe processing shown in FIG. 6 is executed, in S13, the movementprocessing may be performed on a plurality of user data corresponding toa plurality of logical block addresses LBAs.

As described above, the memory controller 3 performs the movementprocessing on the data based on information about the number of the dataread requests from a first storage region (QLC region) of the NANDmemory 4 in which the data is written in a data format of n-bit data toa second storage region (pSLC region) in which the data is written tothe NAND memory 4 in a data format of bit data with the number of bitssmaller than n-bit.

Then, the information on the number of the read requests is the numberof the read requests received by the memory controller 3 from the device(host 2) that outputs the data read requests. The number of the readrequests is counted for each logical address (LBA) of request datarelated to the read request.

FIG. 7 is a flowchart showing an example of a flow of user data movementprocessing when the garbage collection processing is performed. Theprocessing of FIG. 7 is executed when processing of the garbagecollection processing is initiated. In FIG. 7 , the same processingsteps as the processing steps of FIG. 6 are assigned the same stepnumbers and only processing different from the processing of FIG. 6 willbe described.

The CPU 11 searches the management table TBL (S11), and determineswhether there is a logical block address LBA in which the number of theread requests is greater than or equal to the predetermined threshold THin the logical block address LBA of the QLC region (S12). When there isno data whose number of the read requests is greater than or equal tothe predetermined threshold TH in the logical block address LBA of theQLC region (S12; NO), the CPU 11 executes the standard garbagecollection processing (GC processing) (S15).

When there is the logical block address LBA in which the number of theread requests is greater than or equal to the predetermined threshold THin the logical block address LBA of the QLC region (S12: YES), the CPU11 executes processing of moving the user data corresponding to thelogical block address LBA in which the number of the read requests isgreater than or equal to the predetermined threshold TH from the QLCregion to the pSLC region (S13), and updates the L2P table (S14). AfterS14, the CPU 11 executes the GC processing (S15).

Refer to FIG. 4 again. FIG. 4 shows that since the number of the userdata read requests at an address ADDddd is greater than or equal to 200when the predetermined threshold TH is 200, as indicated by the arrowMA, the user data at the address ADDddd is moved from the QLC region toan address ADDbbb in the pSLC region.

As described above, in the memory system 1, the number of the readrequests for each data is tracked in a management table, and the memorysystem. 1 autonomously moves the user data for which the number of theread requests is large from the QLC region (which is a memory regionhaving a slow reading speed) to the pSLC region having a high readingspeed. Accordingly, the reading speed for data that is accessed often isimproved.

According to the above-described embodiment, since the data whosereading frequency is high is stored in the pSLC region in a NAND memory4, the memory system 1 can read the data whose reading frequency is highat a higher speed.

Data with a low reading frequency, even if previously moved to pSLCregion as data having a high reading frequency, may be moved from thepSLC region to the QLC region by using a least recently used (LRU)algorithm or a least frequently used (LFU) algorithm. That is, afterdata is moved into the pSLC region, the memory controller 3 maysubsequently perform move data for which the number of the read requestsis less than some predetermined threshold value from the pSLC region tothe QLC region.

Second Embodiment

The first embodiment describes a case in which the memory controller 3performs the movement processing on the data from the QLC region to thepSLC region based on the number of the read requests from the host 2. Inthe second embodiment, the memory controller 3 performs movementprocessing on data from a QLC region to a pSLC region based oninformation from the host 2.

Since a hardware configuration of a memory system 1A of the secondembodiment is substantially the same as the configuration of the memorysystem 1 of the first embodiment shown in FIGS. 1 and 2 , the samereference numerals are used for the same components, and only differentaspects will be described.

The memory system 1A according to the second embodiment is a systemconforming to a universal flash storage (UFS) standard, and has a hostperformance booster (HPB) function of the UFS standard. The HPB functionis a standard function for flash storage devices.

Since the memory controller 3 of the memory system 1A has the HPBfunction, a part of an L2P table can be transmitted to the host 2according to a request from the host 2. An L2Ps table that is a part ofthe L2P table is cached in the DRAM 2 b on the host 2. As targets of theL2Ps table cached in the DRAM 2 b, the host 2 can set data of “pinnedregion” set by the host 2 and data (active region) which is read manytimes of a logical block address LBA recorded when the host 2 is startedin the past. The host 2 can request the set data of “pinned region” tothe memory system 1A and acquire the data as the L2Ps table. The L2Pstable includes a logical block address LBA and a physical block addressPBA for the set data.

When accessing user data included in the L2Ps table, the host 2 alsotransmits the L2Ps table together to the memory system 1A. That is, thememory system 1A may also receive the L2Ps table together when receivinga read request. The CPU 11 of the memory controller 3 stores the L2Pstable received from the host 2 in a storage region 13 c (indicated by adotted line in FIG. 2 ) of the RAM 13.

The CPU 11 moves the user data from the QLC region to the pSLC regionbased on the L2Ps table. That is, the CPU 11 moves the user datacorresponding to the logical block address LBA included in the L2Pstable from the QLC region to the pSLC region. Further, the CPU 11 alsoupdates the L2P table based on the physical block address PBA of amovement destination for the logical block address LBA.

FIG. 8 is a flowchart showing an example of a flow of data movementprocessing in the present embodiment. When the L2Ps table from the host2 is received, the processing of FIG. 8 is executed by the CPU 11.

The CPU 11 stores the L2Ps table in the storage region 13 c, executesthe processing of moving the user data from the QLC region to the pSLCregion based on the L2Ps table (S21), and updates the L2P table in thestorage region 13 b (S22).

In S21, the user data having a high reading frequency and set by thehost 2 is moved from the QLC region to the pSLC region.

A logical block address LBA of the data of “pinned region” set by thehost 2 and a logical block address LBA of the data (active region) whichis read many times of the logical block address LBA recorded when thehost 2 is started in the past are included in the L2Ps table. Therefore,by moving the user data from the QLC region to the pSLC region based onthe L2Ps table, the memory system 1A can read these data at a highspeed.

Therefore, according to the memory system 1A of the present embodiment,among the data stored in each NAND memory 4, the data having a highreading frequency can be read from the pSLC region at a high speed.

Even in a case of the user data moved to the pSLC region based oninformation from the host 2, data whose reading frequency is low may bemoved from the pSLC region to the QLC region by using a least recentlyused (LRU) algorithm or a least frequently used (LFU) algorithm.

Third Embodiment

In the above-described embodiments, the user data with a large number ofthe read requests is moved from the QLC region to the pSLC region. Inthe third embodiment, in addition to the processing of the first or thesecond embodiment, after moving the data from a QLC region to a pSLCregion based on an L2Ps table, the memory controller 3 tracks the numberof cache hits and the number of cache misses for each piece of data insubsequent reading using data in the pSLC region as cache data. In thiscase, the memory controller 3 performs movement processing on the dataaccording to the number of cache hits and the number of cache misses foreach logical block address LBA.

FIG. 9 shows a configuration of a management table TBL1 for managing thenumber of cache hits and the number of cache misses when reading theuser data in the third embodiment. The management table TBL1 includesthe address of the logical block address LBA included in the L2Ps table,and information on the number of cache hits and the number of cachemisses. The management table TBL1 is stored in the storage region 13 aof the RAM 13 in FIG. 2 , for example.

Immediately after the memory system 1A is started and the L2Ps tabledata is transmitted to the host 2, the address of the pSLC region in themanagement table TBL1 matches the logical block address LBA in the L2Pstable transmitted to the host 2. However, when a cache miss occurs, alogical block address of the QLC region related to the cache miss isalso added to the management table TBL1. Therefore, the management tableTBL1 in FIG. 9 may also include the data for the QLC region or portionsthereof.

FIG. 10 is a flowchart showing an example of a flow of update processingof the management table TBL1. The processing in FIG. 10 is performed bythe CPU 11 reading a program(s) stored in the ROM 12 of the memorycontroller 3, loading the program(s) into the RAM 13, and executing theprogram(s).

The CPU 11 determines whether a read request from the host 2 is received(S31). When the read request is not received (S31; NO), the CPU 11 doesnot perform the update processing of the management table TBL1.

When the read request is received (S31; YES), the CPU 11 tracks thenumber of cache hits and the number of cache misses for the address(logical block address LBA) of the pSLC region in the management tableTBL1 (S32). In S32, based on the logical block address LBA related tothe read request, update processing of the number of cache hits and thenumber of cache misses of the data in the pSLC region in the managementtable TBL1, that is, increment processing of the number of cache hitsand the number of cache misses is performed.

When there is the read request for the data of the logical block addressLBA in the pSLC region, it is determined that there is a cache hit. Whenthere is the read request for the data of the logical block address LBAthat is not in the pSLC region, it is determined that there is a cachemiss. When there is the cache miss, the CPU 11 adds the logical blockaddress LBA of the data related to the cache miss to the managementtable TBL1.

The memory controller 3 updates the number of cache hits and the numberof cache misses of the address (logical block address LBA) of the userdata every time the read request from the host 2 is received.

FIG. 11 is a flowchart showing an example of a flow of user datamovement processing in the third embodiment.

The processing of FIG. 11 may be executed when the read request from thehost 2 is received, or may be executed when predetermined processingother than the read request processing, such as garbage collectionprocessing and compaction processing, is executed, or may be executed ata predetermined cycle (e.g., periodically at fixed intervals of time orthe like).

The CPU 11 searches the management table TBL1 (S41) and determineswhether there is data in which the number of cache hits and the numberof cache misses are greater than or equal to a threshold TH1 (S42). InS42, it is determined whether there is data in which the number of cachehits is greater than or equal to the predetermined threshold TH1 andwhether there is data in which the number of cache misses is greaterthan or equal to the predetermined threshold TH1. That is, the CPU 11sequentially reads each data of the number of cache hits and the numberof cache misses of the management table TBL1 in order, and determineswhether there is the data in which the number of cache hits and thenumber of cache misses are greater than or equal to the predeterminedthreshold TH1.

In this example, whether the number of cache hits or the number of cachemisses are large is determined based on the same threshold TH1. However,in other examples, a threshold value for determining whether the numberof cache hits is large may be different from a threshold value fordetermining whether the number of cache misses is large.

Immediately after the operation of the memory system. 1A, the datadetermined to have a high reading frequency from the host 2 is in thepSLC region. In a subsequent reading of data, the user data that is notinitially in the pSLC region is also moved to the pSLC region when thenumber of cache hits or the number of cache misses increases. FIG. 9shows that the data in the QLC region is moved to the pSLC region asindicated by the arrow MA.

When there is no data having the large number of cache hits or the largenumber of cache misses (S42: NO), the CPU 11 does not perform the userdata movement processing.

When there is the data in which the number of cache hits or the numberof cache misses is greater than or equal to the threshold TH1 in the QLCregion (S42; YES), the CPU 11 moves the user data corresponding to thelogical block address LBA for which the number is greater than or equalto the predetermined threshold TH1 from the QLC region to the pSLCregion (S43).

After moving the user data, the CPU 11 updates the L2P table to thereflect movement of the user data (S44). That is, the physical blockaddress PBA of the moved user data is changed in the L2P table.

As described above, the memory controller 3 performs the movementprocessing on the data based on external information (the L2Ps table)received from an outside (host 2). The memory controller 3, for example,moves data from a first storage region (e.g., a QLC region) of the NANDmemory 4 where the data was written as multilevel data of a n-bit formatto a second storage region (e.g., pSLC region) where the data is writteninto the NAND memory 4 as less than n-bit format data. In some examples,the second storage region may also be written with multilevel data,though of a lower n-bit number than the first storage region.

Further, the external information (the L2Ps table) is information of anexternal device (host 2) that transmits the read request. In the exampledescribed above, the external information (L2Ps table) is informationindicate a part or subset of the address conversion table (L2P table)used for converting the logical address (LBA) of the data into thephysical address (PBA) of the NAND memory 4.

When the data moved to the pSLC region is used as the cache data basedon the external information (the L2Ps table), the memory controller 3counts the number of cache hits and the number of cache misses of thecache data in response to the read request, and performs the movementprocessing on the data between the QLC region and the pSLC region basedon at least one of the number of cache hits or the number of cachemisses.

When the processing shown in FIG. 11 is executed every time there is theread request from the host 2, in S43, the movement processing can beperformed on user data corresponding to one logical block address LBA.However, when the processing shown in FIG. 11 is executed when thegarbage collection processing is performed, in S43, the movementprocessing may be performed on a plurality of user data corresponding toa plurality of logical block addresses LBAs.

Therefore, according to the present embodiment, by using the information(L2Ps table) from the host 2, the data stored in the pSLC region can beset, and the data having a high reading frequency can be read at ahigher speed.

According to an HPB function, when the read request from the host 2 isreceived, the memory controller 3 uses the received L2Ps table toidentify the physical block address PBA corresponding to the logicalblock address LBA related to the read request. Therefore, since the CPU11 does not need to separately refer to the L2P table in the storageregion 13 b, the physical block address PBA corresponding to the logicalblock address LBA related to the read request can be identified morequickly.

Therefore, according to the third embodiment, the L2Ps table related tothe data whose reading frequency is high by the host 2 can be obtainedfrom the host 2, the L2Ps table can be searched, and the physical blockaddress PBA can be acquired at a high speed. Further, since the memorycontroller 3 moves the data having a high reading frequency to the pSLCregion based on the L2Ps table received from the host 2, the memorysystem 1A can read the data whose reading frequency is high at a highspeed.

As described in the above embodiments, it is possible to provide amemory system in which the memory system autonomously moves the datawhose reading frequency is high to a high-speed readable storage region.

Each of the above-described embodiments describes a case in which thememory cell array 4 a of the NAND memory 4 of the non-volatile memory isa QLC type memory cell. However, the memory cell array 4 a may be a TLCtype memory cell or a multiple level cell (MLC) capable of storing 2-bitdata.

In the above examples, a case in which in a QLC type non-volatile memory(capable of storing 4-bit data) was used as the slower storage region,and the high-speed readable storage region was the pSLC region (storing1-bit data) was described. However, the high-speed readable storageregion may be a MLC region storing data of less than 4-bit data. Thehigh-speed readable storage region may also be a single level cell-type(SLC-type) region rather than a pseudo-single level cell-type region.

In some examples, the host 2 could select data to be read at a highspeed and explicitly instruct placement of the data into the pSLCregion. However, in such a case, it is necessary to perform driverdevelopment and program development on the host 2 side to identify andspecify the data to be read at a high speed and then instruct placementof the identified data in the pSLC region. In addition, it would benecessary to consider memory allocation for each data type in advance,and when an unexpected operation occurs, there would be a possibilitythat an event in which the reading speed is significantly delayed mayoccur.

To avoid such problems, since according to the above-describedembodiments, the memory system autonomously places the data having ahigh reading access frequency in the pSLC region based on the readrequests from the host 2 or based on the information supplied by thehost 2 in standard operations, there is no need to perform the driverdevelopment and installation on the host 2 side.

While certain embodiments have been described, these embodiments havebeen presented by way of example only, and are not intended to limit thescope of the disclosure. Indeed, the novel embodiments described hereinmay be embodied in a variety of other forms; furthermore, variousomissions, substitutions and changes in the form of the embodimentsdescribed herein may be made without departing from the spirit of thedisclosure. The accompanying claims and their equivalents are intendedto cover such forms or modifications as would fall within the scope andspirit of the disclosure.

What is claimed is:
 1. A memory system, comprising: a non-volatilememory array including a plurality of memory cells, each memory cellbeing a multilevel cell to which multibit data can be written, thenon-volatile memory array including a first storage region in which themultibit data of a first bit level is written and a second storageregion in which data of a second bit level less than the first bit levelis written, the first and second storage regions each comprisingmultilevel cells that have the same storage capacity as one another; anda memory controller configured to move pieces of data from the firststorage region to the second storage region based on a portion of alogical-to-physical address conversion table received from an externalhost device that sends read requests to the memory controller.
 2. Thememory system according to claim 1, wherein the external information isreceived along with a read request from the external host device.
 3. Thememory system according to claim 1, wherein the memory controller isconfigured to provide a host performance booster function conforming toa universal flash storage (UFS) standard.
 4. The memory system accordingto claim 1, wherein the second bit level is a 1-bit level.
 5. The memorysystem according to claim 4, wherein the first bit level is a 4-bitlevel.
 6. The memory system according to claim 1, wherein thenon-volatile memory array is a NAND flash memory array.